Independent update and assembly of web page elements

ABSTRACT

The invention permits assembly of Web pages for display, to include text elements received from discrete network locations, and permits independent update of individual text elements of a Web page without reassembling the entire Web page, and permits independent update of all types of page elements without a client side agent other than a browser. In one aspect of the invention, a browser at a client device updates the display of a Web page containing at least one first element by transmitting a request to a server for a second element that is related to the first element, receiving the second element, and then displaying the second element with the Web page, without reassembling the Web page. In another aspect of the invention, the transmitting, receiving, and displaying are accomplished without a client side agent other than the browser.

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. ProvisionalApplication No. 60/231,842 filed Sep. 11, 2000.

STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT

[0002] Not Applicable

REFERENCE TO A MICROFICHE APPENDIX

[0003] Not Applicable

BACKGROUND OF THE INVENTION

[0004] 1. Field of the Invention

[0005] The present invention relates generally to display of Web pagesand, more particularly, to assembly and update of Web page elements.

[0006] 2. Description of the Related Art

[0007] The Internet is a computer network that provides access to theWorld Wide Web (“the Web”), a vast collection of pages comprised oftext, graphical, and multimedia elements. Graphical user interfaceprograms called Web browsers are employed by Internet users to receive,or download, the Web pages from servers and display the pages at theirclient computers. A Web browser displays Web pages by showing the textand graphical elements on a client display screen and by playing soundfiles and showing video sequences.

[0008] The rapid increase in the number of Internet users and in theamount of information being downloaded by users has resulted in highvolumes of traffic, as well as increasing delays in downloading Webpages. Delays in downloading pages make an Internet user's browsingexperience less enjoyable. This is especially true for Internet userswho do not have high-speed access to the Internet. The response time forthe transfer of page elements between servers and clients could beimproved if the amount of data traffic passing over the Internet couldbe reduced.

[0009] To download a Web page, a user at a client machine requests a Webpage by sending a Web page address to the corresponding Web server. AWeb page address is specified by a uniform resource locator (URL). Whenthe Web server receives the URL request from a client machine, itdetermines the format and elements of the requested Web page andconstructs a text file according to the hypertext mark-up language(HTML) standard. The HTML file specifies the text to be written and theWeb page elements, such as URLs for image files that are to be viewed ordisplayed, and the format in which they should be presented. The serversends the HTML text file to the client machine, along with anycorresponding data files specified by the HTML code.

[0010] At the client machine, the user's Internet browser receives theHTML code and automatically renders the page elements, displaying thetext data and sending further requests for files specified by URLs inthe HTML code. The requests for files may include, for example, imagefiles at servers other than the server from which the original HTML codewas received. Thus, it should be apparent that displaying a single Webpage may involve many different requests for data and numerous transfersof data between the client machine and one or more Web servers.

[0011] One contributor to the excessive Internet traffic that is slowingdown the Web is the requirement for reloading of Web pages. Typically,each time a user “visits” a Web page by requesting its contents, thatuser's Web browser must reload the page data by requesting the entireHTML code and the corresponding data elements. Although some Web pageshave a large number of elements that change frequently, it is moretypical for a page to be largely static. That is, most of the pageelements will not change. The download of Web pages could proceed muchmore smoothly if all of the elements of a Web page did not need to betransferred from a server every time the page is requested.

[0012] Some Web page source files can be specified in the HTML code,such as graphical images and sound files, so they can be referenced byname and independently requested from corresponding servers. Thegraphical image files are typically among the largest elements of a Webpage and take the most time to download. Thus, browsers may cache suchfiles at the user's computer. When a user requests a Web page, theuser's browser can check for updated graphical image files. If there hasbeen no change between the version stored in the user's cache and theversion to be obtained from the Web server, then the browser will notrequest the server version, and instead will use the cached version.This reduces the number of page elements that must be requested from theInternet, giving the user the appearance of a faster connection, andthereby providing a more pleasurable experience.

[0013] Other developments illustrate the great effort at reducing theamount of data that must be transferred between user (client) computersand the Web servers from which page elements are retrieved. For example,companies have begun to provide a Web cache service whereby they provideintermediate storage of data files at a network location between the Webserver and the user computer. The intermediate storage is typicallydistributed about in multiple network locations to provide fasterresponse to user requests for graphical images. Web cache services workin concert with Web page servers, as follows. When users request a pagefrom a Web server, the Web server assembles the page elements into theHTML file that will be sent to the user browser. The Web serverdetermines which Web server or cache location can most quickly provide agraphical element of the requested page. The Web server places thecorresponding URL in the HTML code that is sent to the user's computer.When the user's browser receives the HTML code, it displays the HTMLtext and requests the graphical elements from the servers indicated bythe Web server. In this way, users should receive page elements morequickly than if all the elements came from the original Web server.

[0014] While such Web cache techniques can deliver graphical images morequickly to users, the cache files are limited to “tagged” files, such asgraphical images (JPEG, GIF, and other image files) and sound files(such as WAV files). The HTML files, and therefore the portions of theWeb page that comprise text, must still be obtained from the originalserver. Moreover, with every page request, all of the page elements willbe requested, even if there have been no changes in the individualelements.

[0015] There presently is no way to independently request download ofindividual elements from a Web page, other than tagged elements. Thus,every time a page reload or refresh operation is initiated by the user,the entire contents of the Web page will be requested from a server, thelone exception being any tagged element files that are cached at theuser's computer. It would reduce the amount of data to be transferredbetween client and server if refresh requests could be processed bydelivering only the updated portions of a Web page, and if suchindependent updates could include elements that are not tagged files,such as Web page text portions.

[0016] Another development that reduces data transfer for display of Webpages is the use of applets written in the “Java” programming language,as developed by Sun Microsystems, Inc. of Mountain View, Calif., USA.Such applets are files of executable code that are received at userclient machines from Web servers and then executed at the client. Thus,the Java applets comprise computer programs that must be received from aserver and then must be executed from within a suitably equipped(Java-enabled) browser.

[0017] A browser typically “pauses” in its page display operations whilea Java applet is being downloaded. Once they are executing, Java appletsgive the user the illusion of dynamic (and continuous) downloadingactivities. That is, to generate an equivalent Web page display withoutthe Java applet, the user would have to continuously download data froma Web server. The Java applet may provide dynamic display of informationin the user's Web browser, but cannot access additional resources on theuser computer, and must be fully downloaded before they can executetheir operations. Moreover, the information displayed by a Java appletcannot be updated independently of the applet itself. Thus, to updatethe Java display, the user must download another version of the Javaapplet. In addition, each time the display is changed, a new applet mustbe written and provided at the Web server.

[0018] From the discussion above, it should be apparent that there is aneed for a quick, efficient means of assembling Web pages for display,to include text elements received from discrete network locations, andthere is a need for independent update of individual elements of a Webpage without reassembling the entire Web page. The present inventionfulfills this need.

BRIEF SUMMARY OF THE INVENTION

[0019] The invention permits independent update of individual displayelements of a Web page without reassembling the entire Web page, andpermits independent update of all types of page elements without aclient side agent other than a browser. Page elements that do notinclude a named source, such as text elements, may nevertheless bereceived from discrete network locations, and therefore they may beindependently assembled and updated. In accordance with the invention, abrowser displays a Web page containing at least one first element of theWeb page and transmits to a server a request for a second element of theWeb page, receives the second Web page element, and then displays thesecond element with the Web page, without reassembling the entire Webpage. Thus, a page reload action does not require the browser to requestall of the named source elements, as well as all the page elements thatdo not include a named source. Rather, only the page elements thatrequire updating need be requested by the browser. In this way, theinvention provides a quick, efficient means of assembling all elementsof a Web page for display, including text elements received fromdiscrete network locations, and supports independent update ofindividual elements of a Web page without reassembling the entire Webpage.

[0020] The browser sends the request for the second element of the Webpage, so that the browser determines when a request for an update of apage element should be sent. Thus, the browser is not limited torequesting only named source elements, or requesting the entire page. Inone aspect of the invention, the browser sends the request for thesecond element in response to a request from an interpreted program, orscript, that executes from within the browser at the client device.Thus, no client-side agents or program applets are involved ingenerating the request for the second element. In this way, it is notnecessary to modify the operation of the browser or install applets orspecial browser plug-in applications to the browser, making the improvedindependent update operation transparent to the user.

[0021] Other features and advantages of the present invention should beapparent and will be better understood by reference to the drawings andthe following detailed description, which illustrate, by way of example,the principles of the invention.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWING

[0022]FIG. 1 shows a system having a client and server constructed inaccordance with the present invention.

[0023]FIG. 2 is a diagrammatic representation of the operations thattake place in response to a request for Web page information from theclient device illustrated in FIG. 1.

[0024]FIG. 3 is a block diagram representation of one of the computersillustrated in FIG. 1.

[0025]FIG. 4 illustrates a Web page that appears on a display of theclient device illustrated in FIG. 1.

[0026]FIG. 5 is a flow diagram that illustrates the processing performedby the client device of FIG. 1 in independently updating a text elementof the Web page illustrated in FIG. 4.

[0027]FIG. 6 is a flow diagram that illustrates the processing performedby the system of FIG. 1 in independently updating an element of the Webpage illustrated in FIG. 4 without reassembling the entire page.

[0028]FIG. 7 is a flow diagram that illustrates the processing performedby the system of FIG. 1 in assembling independent elements of the Webpage illustrated in FIG. 4.

DETAILED DESCRIPTION OF THE INVENTION

[0029] In accordance with the invention, individual display elements ofa Web page may be independently updated without reassembling the entireWeb page. In addition, the independent update may be accomplishedwithout a client side agent other than a browser. Page elements that donot include a named source, such as text elements, may nevertheless bereceived from discrete network locations, and therefore they may beindependently received and assembled. Such features are provided withoutspecial plug-ins or other modifications to a user's browser, and withoutchanges to a server's operations.

[0030] System Configuration

[0031]FIG. 1 shows a system 100 having a client 102 and one or moreservers 104, 106 constructed in accordance with the present invention.The client and server devices 102, 104, 106 communicate with each otherover a shared network 108, such as the Internet. With respect toInternet communications, the user at the client device 102 will receiveinformation for the display of pages from the “World Wide Web” (“theWeb”) in a graphical user interface viewer program 110, such as a Webbrowser, that executes at the client machine 102. The browser willautomatically display the Web pages at the client device so as to showgraphical elements, such as images, show any alphanumeric text, andrender multimedia files, such as sound and video information.

[0032]FIG. 2 shows the communications that take place between a user atthe client device 102 and the Web server 104. As illustrated in FIG. 2,the client 102 requests a Web page from the Web server 104, as specifiedby a page request 202 with a URL address. The client sends the requestthrough a window 204 of the browser 110 (FIG. 1) and in responsereceives HTML code 206 specifying the Web page elements. The HTML codemay direct the user's browser to request files from a server, which maybe either the same server 104 to which the page request was originallysent, or may be a different server 106 (FIG. 1).

[0033] In accordance with the invention, the HTML code 206 returned bythe server 104 to the client 102 includes interpreted program code thatwill cause the browser 110 to request a “phantom” page from a server.The phantom page comprises a page that is associated with a networkaddress (URL) and a second browser window 208, whose contents will notbe displayed. The interpreted program code may comprise any suitableprogram code that is automatically interpreted by the user's browser110, such as the “JavaScript” (JS) standard established by SunMicrosystems, Inc. The JavaScript code will cause the browser 110 toprepare the second window 208, which is used as a proxy or holder forthe phantom page. This second window will be referred to as a proxywindow, and is shown in FIG. 2 with dashed lines to indicate it will notbe displayed by the browser 110. As described further below, the user'sbrowser 110 will automatically prevent display of the second window,which would otherwise show the phantom page, because a page parameter ofthe phantom page will be set to indicate “no display”. The “no display”condition may be achieved through JavaScript, for example, by settingthe page width and page height of the second window to zero.

[0034] In accordance with the invention, the proxy window technique canbe used to independently update a variety of Web page elements,including text elements. For example, text within cells of a table maybe updated with data from a server at regular intervals. In addition,moving a display cursor over a designated text element may cause apop-up window to appear, or clicking on a hyperlink may cause adifferent text box to appear. These different responses to triggeringevents will be described in greater detail below.

[0035] In this way, Web pages may be assembled for display, includingtext elements received from discrete network locations, and individualtext elements of a Web page may be independently updated withoutreassembling the entire Web page. Moreover, all types of page elementsmay be independently updated without a client side agent other than abrowser. Such features are provided without special plug-ins or othermodifications to a user's browser, and without changes to a server'soperations.

[0036] System Devices

[0037] The computer that implements the client side processing, and thecomputer that implements the server side processing, or any othercomputer device of the system, may comprise any conventional computersuitable for implementing the functionality described herein. FIG. 3 isa block diagram of an exemplary computer device 300 such as mightcomprise any of the computing devices shown in FIG. 1. Each computeroperates under control of a central processor unit (CPU) 302, such as anapplication specific integrated circuit (ASIC) from a number of vendors,or a “Pentium”-class microprocessor and associated integrated circuitchips, available from Intel Corporation of Santa Clara, Calif., USA.Commands and data can be input from a user control panel, remote controldevice, or a keyboard and mouse combination 304 and inputs and outputcan be viewed at a display 306. The display is typically a video monitoror flat panel display device.

[0038] The computer device 300 may comprise a personal computer or, inthe case of a client machine, the computer device may comprise a Webappliance or other suitable Web-enabled device for viewing Web pages. Inthe case of a personal computer, the device 300 preferably includes adirect access storage device (DASD) 308, such as a fixed hard disk drive(HDD). The memory 310 typically comprises volatile semiconductor randomaccess memory (RAM). If the computer device 300 is a personal computer,it preferably includes a program product reader 312 that accepts aprogram product storage device 314, from which the program productreader can read data (and to which it can optionally write data). Theprogram product reader can comprise, for example, a disk drive, and theprogram product storage device can comprise removable storage media suchas a floppy disk, an optical CD-ROM disc, a CD-R disc, a CD-RW disc, aDVD disk, or the like. Semiconductor memory devices for data storage andcorresponding readers may also be used. The computer device 300 cancommunicate with the other connected computers over a network 316 (suchas the Internet) through a network interface 318 that enablescommunication over a connection 320 between the network and the computerdevice.

[0039] The CPU 302 operates under control of programming steps that aretemporarily stored in the memory 310 of the computer 300. When theprogramming steps are executed, the pertinent system component performsits functions. Thus, the programming steps implement the functionalityof the system illustrated in FIG. 1. The programming steps can bereceived from the DASD 308, through the program product 314, or throughthe network connection 320, or can be incorporated into an ASIC as partof the production process for the computer device. If the computerdevice includes a storage drive 312, then it can receive a programproduct, read programming steps recorded thereon, and transfer theprogramming steps into the memory 310 for execution by the CPU 302. Asnoted above, the program product storage device can comprise any one ofmultiple removable media having recorded computer-readable instructions,including magnetic floppy disks, CD-ROM, and DVD storage discs. Othersuitable program product storage devices can include magnetic tape andsemiconductor memory chips. In this way, the processing steps necessaryfor operation in accordance with the invention can be embodied on aprogram product.

[0040] Alternatively, the program steps can be received into theoperating memory 310 over the network 316. In the network method, thecomputer receives data including program steps into the memory 310through the network interface 318 after network communication has beenestablished over the network connection 320 by well-known methods thatwill be understood by those skilled in the art without furtherexplanation. The program steps are then executed by the CPU 302 toimplement the processing of the system.

[0041] Page Display

[0042]FIG. 4 shows a Web page 400 that is displayed at the client device102 illustrated in FIG. 1. The Web page will appear, for example, on thedisplay 306 of the client device. FIG. 4 shows that the Web pageincludes typical display artifacts for a computer program that executesin a window operating system (OS) environment, such as that provided bythe “Windows 2000” or “Windows NT” OS by Microsoft Corporation or the“MacIntosh” OS by Apple Computer Corporation. Thus, the Web page windowdisplay 400 includes a title bar 402 and window sizing icons 404 at thetop of the page. The bottom of the page window includes a program tray406 in which various program icons may be placed.

[0043] On the display, within a working space or display area 408 of thepage window 400, are the contents, or page elements, of a requested Webpage. As illustrated in FIG. 4, these elements may be displayed, orrendered, in a variety of ways. For example, the page 408 may include abanner image 410 that is typically a graphic image, such as representedby a GIF file or JPEG file. The page 400 may also include lines of textinformation, such as illustrated by “Text Information Line 1” 412, TextInformation Line 2“414, and Text Information Line 3” 416. The page mayalso include other images 418, typically in a graphical format, such asGIF or JPEG formats. Web pages may also include tables 420 ofinformation, comprising text or other elements arranged in rows andcolumns. Lastly, Web pages may include multimedia viewers 422, such asfor display of streaming video content or audiovisual clips. The viewersmay include, for example, the “RealPlayer” viewer from Real Networks,“Quick Time” viewer from Apple Computer, Inc., and “Media Player” fromMicrosoft Corporation. The viewers generally include on-screen playbackcontrols 424 that permit a user to move forward, reverse, or pause theplayback.

[0044] Conventionally, only the graphic images 410, 418 and themultimedia content played by the viewer 422 may be independently updatedfrom the remaining elements of the page. This is because such graphicimages and multimedia files are identified by image tags of the HTMLcode. The image tags specify the server (URL) at which the graphic maybe found and from which the graphic must be requested. Those skilled inthe art will appreciate that a request for a Web page causes acorresponding Web server to generate the HTML code for the Web page,much of which comprises alphanumeric text that a user's browser willthen render and display. For graphic and multimedia files, the Webserver will deliver alphanumeric HTML text and, where appropriate, willembed URL addresses that specify the network locations at which thegraphical images may be found. When the client browser receives the HTMLcode from the Web server, the browser will automatically render the HTMLcode to generate the proper text. When the client encounters an embeddedHTML code specifying a URL address, the browser will automatically sendout another request, this time for the specified URL of the graphicalimage element. The request will be sent to the server at the URLspecified in the address. When the graphical image is returned, theuser's browser will automatically render the image and display it withthe other elements of the Web page.

[0045] Operation

[0046]FIG. 5 is a diagrammatic representation of the processingperformed by the system of FIG. 1 in independently updating andassembling the Web page illustrated in FIG. 4. As indicated in FIG. 5,the processing begins with the client 102 sends a request for a Web pageto the server 104. This operation is indicated as “1. URL PAGE REQUEST.”In response, the server retrieves or generates the HTML code for the Webpage and sends it to the client. This operation is represented by thesecond FIG. 5 entry, “2. SEND HTML FILE TO CLIENT MACHINE FOR DISPLAY.”When the client receives the Web page data, the client's browserinterprets the HTML code to display the proper text, and requests theappropriate source files, such as graphic images, sound files, ormultimedia presentations. This operation is represented in FIG. 5 by thenotation “3. RENDER HTML DATA, PROCESS SOURCE TAGS, REQUEST IMAGES.” Thevarious files specified in the HTML code for the page will be thesubject of corresponding file requests from the browser. The browserrequests are received at the Web server (which may or may not be thesame server from which the client first requested the Web page), and theWeb server responds by returning the requested files. This operation isrepresented by the fourth entry, “4. GET IMAGES AND OTHER REQUESTEDFILES, SEND TO CLIENT MACHINE.”

[0047] As noted above, the system of FIG. 1 utilizes a scriptinglanguage to cause the client browser to automatically generate requestsfor update data, with which the browser may update Web page elementsthat do not otherwise have a named source. These elements to be updatedmay include text information, such as table contents. Therefore, therequest for files in operation (3) includes a request for a scriptingfile. The scripting language may comprise, for example, the “JavaScript”specification from Sun Microsystems, Inc. The Web server response, inoperation (4), will be to generate a JavaScript file that containsscript code that will cause the client's browser to generate a requestfor update data.

[0048] Thus, the HTML code that the client receives from the server as aresult of operation (2) will include a reference to a JavaScript file ata Web server. This reference is processed as follows. As the clientbrowser renders (displays) the Web page in operation (3), it will parsethe received HTML code. Portions of the HTML code will include formattedalphanumeric text, which the browser will display, and will includereferences to source files, such as images, and also to audio andmultimedia files, and the like. In accordance with the invention, theHTML code will also include a reference to a JavaScript file thatimplements the functionality described herein. When the client's browserparses the received page code and encounters the JavaScript reference inoperation (3), the browser will generate a request to the Web serverreferenced by the JavaScript. The Web server will receive the requestand in operation (4) will generate the appropriate JavaScript code anddeliver it to the client browser, as will any requested source filessuch as images, sounds, and the like. Thus, the reference to aJavaScript file is converted into actual JavaScript code that is placedat the appropriate location in the HTML code for the Web page.

[0049] When the JavaScript code is received, it will be automaticallyinterpreted by the browser, which will cause the script program to beexecuted by the browser. In accordance with the invention, theJavaScript code will cause the browser to request another page, for asecond Web page. This operation is represented by the fifth entry ofFIG. 5, “5. RECEIVE SCRIPT, INTERPRET CODE, REQUEST UPDATE PAGE.” TheJavaScript code in accordance with the invention specifies that therequested second page will not be displayed by the browser. That is, thedata contained in the second (update) page will be received, but no pagewill be displayed. Thus, the requested page comprises a “phantom” page(hence the dashed line representation of FIG. 2). When the Web serverreceives the request for the phantom page after operation (5), it willgenerate the requested data and will send it (otherwise formatted as anHTML page) to the browser. The sending operation is represented in FIG.5 by the sixth entry, “6. SEND REQUESTED HTML DATA FOR PHANTOM PAGE.”

[0050] When the client browser receives the requested update data, itprocesses the data according to the JavaScript code to perform whatevertask has been specified by the Web page author or developer for displaywithin the original Web page window, rather than in the phantom secondwindow. For example, the updated data may call for placement in a cellof a table in the original Web page, thereby updating the table values.The updated data may be for placement in a special data window, such asa stock market price ticker or an auction site bid window of the firstWeb page. In any case, the operation of displaying the updated data inthe first Web browser window is represented by the FIG. 5 entry of “7.PROCESS THE JAVASCRIPT CODE AND DISPLAY THE FIRST WEB PAGE WITH THEUPDATE DATA.”

[0051] Because the JavaScript code as described above can use thebrowser to request a new page from a Web server, and information fromthe new page can be extracted by the browser and inserted into theoriginal page, the JavaScript code can be used to independently updateWeb page elements that previously could not be updated separately fromother alphanumeric text elements on the page. For example, a table maybe updated using the technique described herein to independently updateparticular table cells.

[0052] The present invention has been described above in terms ofpresently preferred embodiments so that an understanding of the presentinvention can be conveyed. There are, however, many configurations fornetwork data delivery not specifically described herein, but with whichthe present invention is applicable. The present invention shouldtherefore not be seen as limited to the particular embodiments describedherein, but rather, it should be understood that the present inventionhas wide applicability with respect to network data delivery generally.All modifications, variations, or equivalent arrangements andimplementations that are within the scope of the attached claims shouldtherefore be considered within the scope of the invention.

We claim:
 1. A method for independently updating individual displayelements of a Web page on a client device, the method comprising:displaying, in a browser window of a client device, a Web pagecontaining at least one first element of the Web page; transmitting, toa server, a request for a second element of the Web page that is relatedto the first element; receiving at the client device the second Web pageelement; and displaying the second element with the Web page, withoutreassembling the Web page.
 2. A method as defined in claim 1, whereintransmitting, receiving, and displaying the second element areaccomplished without a client device agent other than a Web browser. 3.A method as defined in claim 1, wherein the second element replaces thefirst element on the displayed Web page.
 4. A method as defined in claim3, wherein transmitting the request for the second element is responsiveto a timer event.
 5. A method as defined in claim 3, whereintransmitting the request for the second element is responsive to amouse-over event.
 6. A method as defined in claim 3, whereintransmitting the request for the second element is responsive to a mouseclick event.
 7. A method as defined in claim 1, wherein the secondelement augments the first element on the displayed Web page.
 8. Amethod as defined in claim 7, wherein transmitting the request for thesecond element is responsive to a timer event.
 9. A method as defined inclaim 7, wherein transmitting the request for the second element isresponsive to a mouse over event.
 10. A method as defined in claim 7,wherein transmitting the request for the second element is responsive toa mouse click event.
 11. A method as defined in claim 7, wherein thesecond element is displayed in a pop-up window in the browser window.12. A method as defined in claim 7, wherein the second element isproduced by a browser window action.
 13. A method as defined in claim 7,wherein the second element provides a responsive hyperlink of thebrowser window.
 14. A method as defined in claim 1, wherein the secondelement is received by the client device from the server.
 15. A methodas defined in claim 1, wherein the second element is received by theclient device from a computer other than the server.
 16. A method asdefined in claim 1, wherein the second element is a text element.[claims 17-20 intentionally left blank]
 21. A method for updatingdisplaying of an element of a Web page, the method comprising:displaying in a browser window of a client device a Web page containingat least one first element of the Web page; transmitting, to a server, arequest for a second element that is related to the first element;receiving at the client device the second element; and displaying thesecond element with the Web page, without reassembling the Web page;wherein transmitting, receiving, and displaying the second element areaccomplished without a client device agent other than a Web browser. 22.A method as defined in claim 21, wherein the second element comprises atext element to be displayed with the Web page.
 23. A method as definedin claim 22, wherein the second element comprises a text element and atleast one source element to be displayed with the Web page.
 24. A methodas defined in claim 23, wherein the source element comprises a soundfile.
 25. A method as defined in claim 23, wherein the source elementcomprises an image file.
 26. A method as defined in claim 23, whereinthe source element comprises a video file.
 27. A method as defined inclaim 23, wherein the source element comprises a streaming multimediafile.
 28. A method as defined in claim 21, wherein the second elementcomprises a source element to be processed by the browser.
 29. A methodas defined in claim 28, wherein the source element comprises an imagefile.
 30. A method as defined in claim 28, wherein the source elementcomprises an applet.
 31. A method as defined in claim 21, wherein thesecond element replaces the first element on the displayed Web page. 32.A method as defined in claim 31, wherein transmitting the request forthe second element is responsive to a timer event.
 33. A method asdefined in claim 31, wherein transmitting the request for the secondelement is responsive to a mouse over event.
 34. A method as defined inclaim 31, wherein transmitting the request for the second element isresponsive to a mouse click event.
 35. A method as defined in claim 21,wherein the second element augments the first element on the displayedWeb page.
 36. A method as defined in claim 35, wherein transmitting therequest for the second element is responsive to a timer event.
 37. Amethod as defined in claim 35, wherein transmitting the request for thesecond element is responsive to a mouse over event.
 38. A method asdefined in claim 35, wherein transmitting the request for the secondelement is responsive to a mouse click event.
 39. A method as defined inclaim 35, wherein the second element is displayed in a pop-up window inthe browser window.
 40. A method as defined in claim 35, wherein thesecond element is produced by a browser window action.
 41. A method asdefined in claim 35, wherein the second element provides a responsivehyperlink of the browser window.
 42. A method as defined in claim 21,wherein the second element is received by the client device from theserver.
 43. A method as defined in claim 21, wherein the second elementis received by the client device from a computer other than the server.[claims 44-60 intentionally left blank]
 61. A method of assembling anddisplaying a Web page at a client device, the method comprising:receiving at the client device, browser display instructions specifyingthe format of the Web page and the location of at least one text elementto be displayed on the Web page; retrieving the text element from thespecified location; inserting the text element into the Web page inaccordance with the specified format; and displaying the Web page in thebrowser window.
 62. A method as defined in claim 61, wherein retrievingand inserting the text element are accomplished without a client deviceagent other than a Web browser.
 63. A method as defined in claim 61,wherein the text element is received by the client device from theserver.
 64. A method as defined in claim 61, wherein the text element isreceived by the client device from a computer other than the server. 65.A method as defined in claim 61, further comprising updating thedisplayed Web page without refreshing the entire page.
 66. A method asdefined in claim 65, further comprising receiving an updated textelement of the displayed Web page.
 67. A method as defined in claim 65,further comprising receiving an updated source element of the displayedWeb page. [claims 68-100 intentionally left blank]
 101. A method asdefined in claim 1, wherein said client device is a personal computer.102. A method as defined in claim 1, wherein said client device is ahandheld device.
 103. A method as defined in claims 101 and 102, whereinsaid second element is not a multimedia or image file.
 104. A method asdefined in claim 103, wherein no browser plug-ins are utilized.
 105. Amethod as defined in claim 104, wherein no Java Applets are utilized.106. A method as defined in claim 105, wherein transmitting a requestfor the second element of the Web page occurs after the HTTP connectionhas terminated.
 107. A method as defined in claim 106, wherein theserver utilizes non-Microsoft Web server software.